Ribbon SBC Edge R11.0 Interop with Microsoft Survivable Branch Appliance using Poly Teams Phone : Interoperability Guide

Interoperable Vendors

Copyright

© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved. The compilation (meaning the collection, arrangement and assembly) of all content on this site is protected by U.S. and international copyright laws and treaty provisions and may not be used, copied, reproduced, modified, published, uploaded, posted, transmitted or distributed in any way, without prior written consent of Ribbon Communications Inc.

The trademarks, logos, service marks, trade names, and trade dress (“look and feel”) on this website, including without limitation the RIBBON and RIBBON logo marks, are protected by applicable US and foreign trademark rights and other proprietary rights and are the property of Ribbon Communications Operating Company, Inc. or its affiliates. Any third-party trademarks, logos, service marks, trade names and trade dress may be the property of their respective owners.  Any uses of the trademarks, logos, service marks, trade names, and trade dress without the prior written consent of Ribbon Communications Operating Company, Inc., its affiliates, or the third parties that own the proprietary rights, are expressly prohibited.

Document Overview

This document outlines the configuration best practices for the Ribbon solution covering the Ribbon SBC Edge when deployed with Microsoft Teams vSBA (virtual Survivable Branch Appliance) and the Teams Phone (Poly CCX 600).

About Ribbon SBC Edge

A ​Session Border Controller​ (​SBC​) is a network element deployed to protect​ ​SIP​-based Voice over Internet Protocol​ (VoIP) networks. ​Early deployments of SBCs were focused on the borders between two service provider networks in a peering environment. This role has now expanded to include significant deployments between a service provider's access network and a backbone network to provide service to residential and/or enterprise customers. ​

The SBC Edge (SBC 1000/2000) addresses the next-generation needs of SIP communications by delivering embedded media transcoding, robust security, and advanced call routing in a high-performance, small form-factor device enabling service providers and enterprises to quickly and securely enhance their network by implementing services like SIP Trunking, secure Unified Communications, and Voice over IP (VoIP).

The SBC Edge provides a reliable, scalable platform for IP interconnect to deliver security, session control, bandwidth management, advanced media services, and integrated billing/reporting tools in an SBC appliance. This versatile series of SBCs can be deployed as peering SBCs, access SBCs, or enterprise SBCs (eSBCs). The SBC product family is tested for interoperability and performance against a variety of third-party products and call flow configurations in the customer networks.

About Microsoft Survivable Branch Appliance (SBA)

When a customer site using Direct Routing to connect to Microsoft Phone System experiences an internet outage, the intranet inside the branch is still fully functional. Users can connect to the Session Border Controller (SBC) that is providing the PSTN connectivity.

During an internet outage, the Teams Phone should switch to the SBA automatically. No action is required from the user. As soon as the Teams Phone detects that the internet service is restored and any outgoing calls are finished, the Teams Phone will fall back to normal operation mode and connect to other Teams services.

The interoperability compliance testing focuses on verifying inbound and outbound call flows between the Ribbon SBC Edge, Teams vSBA, and Teams Phone.

About Poly CCX 600 Business Media Phone, Teams Edition

Poly creates premium audio and video products so you can have your best Microsoft Teams meeting—anywhere, anytime, every time. Poly Teams certified headsets, video and audio-conferencing products, and desk phones are engineered to connect people seamlessly across the world.

Poly CCX 600 is a 7 inch multi-touch LCD display, with 2 USB ports (type A and type C), integrated Bluetooth, and Wi-Fi. It has a dedicated Microsoft Teams button, crystal clear sound with Poly HD Voice, Acoustic Fence, and NoiseBlockAI technologies.

The native Microsoft Teams experience on this CCX phone provides a consistent user experience. The dedicated Teams button is there for one-button access to the new features Microsoft delivers. The color touch screen puts contacts and meetings one tap away. The larger screen on the CCX 600 makes you more productive. Robust provisioning and management options make this phone easy for IT to support.

This guide contains the following configuration sections: 

• Section A: Ribbon SBC Edge Configuration
  
  • Captures general SBC Edge configurations for deploying SBC with Teams vSBA.
• Section B: Microsoft SBA Configuration

  • Captures the Microsoft SBA configuration.

• Section C: Poly CCX 600 Configuration

  • Captures the Poly CCX 600 configuration.

• Basic Calls and Call Hold/Resume features can be tested with configurations from Section A, Section B and Section C.

Non-Goals

It is not the goal of this guide to provide detailed configurations that will meet the requirements of every customer. Use this guide as a starting point and build the SBC configurations in consultation with network design and deployment engineers. 

Audience

This is a technical document intended for telecommunications engineers with the purpose of configuring both the Ribbon SBCs and the third-party product.

To perform this interop, you need to:

• use the graphical user interface (GUI) or command line interface (CLI) of the Ribbon product.
• understand the basic concepts of TCP/UDP/TLS and IP/Routing.
• have SIP/RTP/SRTP to complete the configuration and for troubleshooting.

Prerequisites

The following aspects are required before proceeding with the interop:

• Ribbon SBC Edge
• Poly CCX 600 (Teams Phone)
• Public IP Addresses
• Microsoft admin account - a special type of account where the Teams user can be configured for Direct Routing SBA (Survivable Branch Appliance).
• TLS Certificates for the Ribbon SBC Core signed by one of the Microsoft approved CA vendors.
• Certificates must have the FQDN or domain name that is configured on the Microsoft admin portal.

Product and Device Details

The sample configuration in this document uses the following equipment and software:

Network Topology Diagram

This section covers the Ribbon SBC Edge deployment topology and the Interoperability Test Lab Topology.

Deployment Topology - Ribbon SWe Edge

Ribbon SWe Edge Deployment Topology

Interoperability Test Lab Topology - Ribbon SWe Edge

The following lab topology diagram shows connectivity between Ribbon SWe Edge on virtual platform, Microsoft SBA, and Teams Phone (Poly CCX 600).

SWe Edge and Microsoft SBA interoperability Test Lab Topology

Deployment Topology - Ribbon SBC 2K

Ribbon SBC 2K Deployment Topology

Interoperability Test Lab Topology - Ribbon SBC 2K

The following lab topology diagram shows connectivity between Ribbon SBC 2K, Microsoft SBA, and Teams Phone (Poly CCX 600).

Ribbon SBC 2K and Microsoft SBA interoperability Test Lab Topology

Document Workflow

The sections in this document follow the sequence below. The reader is advised to complete each section for successful configuration.

Section A: Ribbon SBC Edge Configuration

The following SBC Edge configurations are included in this section:

Connectivity

Network

Static Routes

TLS Configuration between SBC Edge and Microsoft SBA

Easy Config Wizard

• SBC Edge can connect to the network as mentioned in Connectivity and Network.
• Microsoft SBA prefers transport as TLS. Establishing a TLS connection between the SBC Edge and Microsoft SBA is covered under TLS Configuration between Ribbon SBC Edge and Microsoft SBA.
• Configure the SBC Edge with PSTN, Teams Direct Routing, and Teams Direct Routing SBA using Easy Config Wizard.

Connectivity

SBC 2000 Front Panel

               

SWe Edge Connectivity

Network

Configure Ethernet 1, Ethernet 3, and Ethernet 4 of SBC SWe Edge with the IP as follows:

Navigate to Networking Interfaces > Logical Interfaces.

Logical Interfaces

 

Static Routes

Static routes are used to create communication to remote networks. In a production environment, static routes are mainly configured for routing from a specific network to a network that can only be accessed through one point or one interface (single path access or default route).

Static routes need to be added towards the Eth1 interface 172.16.X.X (PSTN) and the Eth2 interface 172.16.X.X (ZPLS).

The default static route is towards the Eth1, which is in a private network.

• Navigate to Settings > Protocol > IP > Static Routes to configure the routes.

Static Routes

TLS Configuration between SBC Edge and Microsoft SBA

Prerequisites:

• For TLS to work on the public side of the network, a trusted Certificate Authority (CA) is needed. In this scenario, Go Daddy is used as a trusted CA.

• Go Daddy Root Certificate Authority G2 and Go Daddy Secure Certificate Authority G2 is used as a trusted CA.

• Baltimore CyberTrust Root certificate is required.

Request a certificate for the SBC and configure it based on the example using Go Daddy as follows:

• Generate a Certificate Signing Request (CSR) and obtain the certificate from a Certificate Authority.
• Import the Public CA Root/Intermediate Certificate and the SBC Certificate on the SBC.
  

Step 1: Generate a Certificate Signing Request and obtain the certificate from a Certificate Authority (CA).

• Navigate to Settings > Security > SBC Certificates.
• Click Generate SBC Edge CSR.
• Enter data in the required fields. Click OK. After the Certificate Signing Request is generated, copy the result to the clipboard.

• Use the generated CSR text from the clipboard to obtain the certificate. 

Step 2: Deploy the Root/Intermediate and SBC certificates on the SBC.

After receiving the certificates from the certificate authority, install the SBC Certificate and the Root/Intermediate certificates as follows:

• Obtain the Trusted Root and Intermediary signing certificates from your Certificate Authority.
• To install the Trusted Root/Intermediate certificates, go to Settings > Security > SBC Certificates > Trusted Root Certificates.
• Click Import and select the trusted root certificates.
• To install the SBC certificate, open Settings > Security > SBC Certificates > SBC Edge Certificate.

• Validate the certificate is installed correctly.

Trusted CA Certificate Table

• Click Import and select X.509 Signed Certificate.
• Validate that the certificate is installed correctly.

Validate certificate

Easy Config Wizard

Configure the SBC Edge with Teams Direct Routing SBA using the Easy Config Wizard.

• Access the WebUI of SBC Edge.
• Click on the Tasks tab.
• From the left side menu, click SBC Easy Setup > Easy Config Wizard.

Easy Config Wizard

Fill in the details for Step 1 as follows:

• Application SIP Trunk↔Microsoft Teams.
• Scenario Description as Teams SBA.
• SIP Sessions as 100.

Step 1

Fill in the details for Step 2 as follows:

• Border Element Server would be the PSTN IP.
• Use Secondary Border Element Server should be Disabled.
• Teams Connection Type would be Standalone Direct Connection.
• SBC Signaling/Media Source IP towards Teams Direct Routing (public IP).
• Configure Direct Routing SBA should be set to True.
• Direct Routing SBA FQDN as ioteamsba.customers.interopdomain.com.
• SBC Signaling /Media Source IP towards Teams Direct Routing SBA.

Review the configurations in Step1 and Step 2, and click on the Finish button.

Section B: Microsoft SBA Configuration

For information on configuring the Survivable Branch Appliance (SBA) for Direct Routing, refer to following link:

https://docs.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance

For the Prerequisites, Installation, and Configuring the Direct Routing SBA, refer to following link:

https://doc.rbbn.com/display/UXDOC110/Best+Practice+-+Configure+Direct+Routing+Virtual+Survivable+Branch+Appliance#

Prerequisites

For Prerequisites on Direct routing SBA, refer to the following link:

https://doc.rbbn.com/display/UXDOC110/Best+Practice+-+Configure+Direct+Routing+Virtual+Survivable+Branch+Appliance#BestPracticeConfigureDirectRoutingVirtualSurvivableBranchAppliance-Prerequisites

Installation

For Installation on Direct routing SBA, refer to Step 1 in the following link:

https://doc.rbbn.com/display/UXDOC110/Best+Practice+-+Configure+Direct+Routing+Virtual+Survivable+Branch+Appliance#BestPracticeConfigureDirectRoutingVirtualSurvivableBranchAppliance-Step1:InstallVirtualSBASoftware

Configuration

For Configuring on Direct routing SBA, refer to Step 2 in the following link:

https://doc.rbbn.com/display/UXDOC110/Best+Practice+-+Configure+Direct+Routing+Virtual+Survivable+Branch+Appliance#BestPracticeConfigureDirectRoutingVirtualSurvivableBranchAppliance-Step2:SetuptheOffice365DirectRoutingvSBA

Section C: Poly CCX 600 Configuration

• Log into Web UI of the phone using the IP address.
• Provide the credentials to log into Web UI of the Polycom CCX 600.
• Navigate to Simple Setup > Base Profile and choose "Microsoft Teams".

Polycom CCX Base Profile

• Once the Base profile is selected, wait for the phone to reboot.
• Go to the Polycom CCX phone touch interface. Log into Microsoft Teams on phone, using Teams credentials created as mentioned in Section B.

Supplementary Services and Features Coverage

The following checklist depicts the set of services/features covered through the configuration defined in this Interop Guide. 

Legend

Caveats

The following items have been observed during this Interop - these are either limitations, untested elements, or useful information pertaining to the Interoperability:

• Poly CCX 600 Phones would switch to Survivable Mode when there is an internet outage. It would take around 5-8 mins for the Teams phone to switch to Survivable mode.
• Message on the Teams phone in Survivable Mode - "No internet connection. Calling, including emergency calls, is only available to and from phone numbers". This indicates that the Teams phone is now registered or connected with Microsoft SBA.
• Poly CCX 600 would reach to Microsoft SBA by resolving it's FQDN. Hence the Poly phone secondary DNS server IP needs to be configured, which would resolve the FQDN locally, when there is an internet outage.
• Teams User status would be "Offline" in Survivable mode.

Support

For any support related queries about this guide, contact your local Ribbon representative, or use the details below:

• Sales and Support: 1-833-742-2661
• Other Queries: 1-877-412-8867
• Website: https://ribboncommunications.com/services/ribbon-support-portal

References

For detailed information about Ribbon products & solutions, go to:

https://ribboncommunications.com/products

For information about Microsoft products & solutions, go to:

https://docs.microsoft.com/en-us/microsoftteams/

For information about Poly products & solutions, go to:

https://www.poly.com/in/en/products/phones/ccx/ccx-600

Conclusion

This Interoperability Guide describes a successful configuration of the Ribbon SBC Edge, Microsoft Survivable Branch Appliance, and Poly Teams .

All features and capabilities tested are detailed within this document - any limitations, notes, or observations are also recorded in order to provide the reader with an accurate understanding of what has been covered, and what has not.

Configuration guidance is provided to enable the reader to replicate the same base setup - there maybe additional configuration changes required to suit the exact deployment environment.

© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.